The code looks good, but I would love to see it in action before merging and what are the impacts from a development perspective, if there are any? And probably it's helpful if we have the option run this locally as well, would make dev faster.

@Kammerlo your workflow should not change drastically using this action. At least that was the intention. The action simply makes it easier to get application builds based on your feature branch in cf-reeve-platform which you are working on. So the intended workflow would be that you create a PR in cf-reeve-platform and start working on your features there. This should be true for most of our features. As soon as you start pushing changes to that feature branch the resulting platform version gets synced to the same branch in cf-reeve-application. If there was no branch with the exact same name found, a new branch and a PR will be opened.
This also ensures that all API and E2E tests are executed in a timely manner since change in cf-reeve-platform always trigger commits in cf-reeve-application.